fix: use backstage fetch api instead of the default fetch for node js #180
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Backstage provides a FetchApi to make requests this allows backstage users to create fetch customizations like automatic header
injections. This Pr modifies the announcements plugin to use the backstage fetch api, making it compatible with any backstage implementation using any fetch api customization.
Changes
Additional Comments
The request object was removed as it was causing problems with the fetch api from backstage, the parameters were passed directly to the fetch call instead
Reference
Fetch Api Reference: https://backstage.io/docs/reference/core-plugin-api.fetchapi/